Support use of OmnipodKit#2426
Open
marionbarker wants to merge 1 commit intodevfrom
Open
Conversation
* when OmniBLE or OmniKit was used to start pod, this code allows OmnipodKit to control pod, * this is a one-way trip from OmniXXX to OmnipodKit for that pod
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Allow the new pump manager, OmnipodKit, to work with an already paired pod using Loop.
Overview
OmnipodKit supports all pod types.
Eventually OmniBLE and OmniKit will be discarded.
Modification
This modification enables OmnpodKit pump manager to take over control of a Classic or DASH pod already paired with Loop for the case where OmniBLE and OmniKit have been removed as submodules in LoopWorkspace.
If the submodules for OmniBLE and/or OmniKit are present, then they continue controlling the pod.
Warning
If you build a LoopWorkspace which has OmnipodKit but not OmniBLE and OmniKit, then it is a one-way trip for that pod.
You cannot go back to a build with does not have OmnipodKit installed without changing pods.